An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I need to vent some real frustration with App Review. Our app "AlphaOmega" has been live on the App Store since July 6, 2026. We submitted a routine update (version 1.0.4, not a new app) on July 11. It sat untouched in the review queue for 10 full days before anyone even looked at it. For an update to an already-approved, already-live app, that's not acceptable. And when it finally got reviewed on July 21, we got rejected under Guideline 4.1(a) "Copycats," with this justification: "Specifically, the app's icons include references to Omegle." That's it. No screenshot comparison, no explanation of what "reference" means. I put our icon next to Omegle's actual icon myself (attached below): Ours: white Greek letters Α/Ω overlapped, purple gradient background Omegle's: a blue background with a white comma-shaped swirl They share nothing — not color, not shape, not any design element. Our app name comes from the Christian phrase "Alpha and Omega," has nothing to do with "Omegle" beyond a partial spelling overlap. This isn't a borderline case that needs interpretation — it's just wrong. We've already replied to the review message with this clarification and separately submitted a formal appeal to the App Review Board. We also requested an expedited review — it made no difference. What makes this especially hard is that we built this app so our church community could finally have it. People have been anxiously checking in day after day, hoping to be able to use it together. This is how the cycle usually goes for us: submit, sit in the queue for days waiting for a reviewer to even look at it, sit in "In Review" for days more, then get rejected for a reason that doesn't hold up to two minutes of scrutiny — fix it, resubmit, and start the whole cycle again, with no guarantee the next rejection will even make sense. We've stayed up late more than once just to catch a review update, only for it to end exactly like this. Is this really how Apple treats developers? At this point I'm seriously reconsidering whether I want to keep building for iOS at all. So right now: 10 days to get a wrong answer, a canned one-line rejection with zero evidence, and I have to spend more time writing replies and appeals just to get a human to actually look at two icons side by side. Meanwhile the update sits blocked with no ETA. Is this the normal experience now? Anyone else dealing with 10+ day waits for simple updates, followed by rejections that don't hold up under two minutes of scrutiny? App Information: App Name: AlphaOmega Apple ID: 6783182206 Bundle ID: com.zoven.omega Platform: iOS Version rejected: 1.0.4 (build 26)

Hi all, I'm hoping someone has seen this before. My app's first submission was rejected, but I cannot find the rejection reason anywhere. What I see: The app-level status shows "Rejected". Under App Review, the submission itself still shows "In Review". There is no reviewer message / no Resolution Center message anywhere, and the in-app purchases are all marked as rejected too. The rejection email only says to visit the App Review page, but the link just opens the App Store Connect root (appstoreconnect.apple.com) with no details. What I already tried: App Store Connect on web (Safari/macOS and Firefox/Windows) and the App Store Connect iOS app — all three show the exact same state. Hard reload, private window, sign out / sign back in. Opened an App Review contact request asking for the specific reasons — no response until now. So the app is clearly rejected, but the submission status and the reviewer feedback never propagated on my end. It looks like a backend status/desync issue. Questions: Has anyone experienced this "rejected but stuck on In Review with no message" state? Where else can the rejection details appear, or is it purely a matter of waiting for the backend to sync? Roughly how long did it take to resolve for you? App: CountTally Submission ID: e9bf771c-a5a2-471f-9db4-7b7038d4ebf9 Thanks a lot for any pointers!

Hello, I'm looking for advice from other developers who may have experienced unusually long App Review times. Here is my situation: • I submitted five apps on March 2, 2026. • They remained in Waiting for Review until the end of April. • They have now been In Review for several months. • I also submitted CampusGo Connect on May 14, 2026, and it is still Waiting for Review. I have contacted Apple Developer Support several times. They confirmed that my apps are still in the review process, but there have been no updates or requests for additional information. I have also verified that my Apple Developer Program membership is active, all agreements are accepted, and my App Store Connect account is functioning normally. Has anyone experienced review times this long? If so: • How long did your review eventually take? • Was there anything you did that helped? • Is there anything else I should try besides continuing to work with Developer Support? Thank you for any advice.

Hello, My first App Store submission (Apple ID 6769883617) has been stuck in "Waiting for Review" since July 12. Timeline: July 12: Submitted for review. July 18: Expedited review requested and approved. July 19: Contacted App Review through Contact Us / App Review Status. July 21: Still no status change and no response. I understand that review times can vary, but over 9 days in "Waiting for Review", an approved expedited request, and no reply from App Review no longer seems like a normal review timeline. Has anyone experienced this recently? Is there another way to reach the App Review team or verify that my submission isn't stuck? Any guidance would be appreciated. Thank you.

Hello, Our app submission has remained in “Waiting for Review” since 7/14. App: Skald: Odyssey Apple ID: 6790579937 Version: iOS 0.1.0 Support case: 102944762837 We contacted Developer Support on 7/17 and submitted the App Review status/contact form on 7/21, but have not received a response. App Store Connect does not show any action required from us. The submission metadata, review notes, contact information, demo credentials, and backend access are complete and available. Could an Apple representative please confirm that the submission is correctly queued and escalate the case if necessary? This delay is now significantly longer than our usual review times, and we have been unable to get a status update through the normal support channels. We would appreciate confirmation that the submission is not stuck and that no action is required from us. Thank you.

Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.

Hello App Review team, My app (App ID: 6745896828) was rejected on Friday, July 17. I addressed the points raised and resubmitted the same day. Since then, the build has stayed in "Waiting for Review" with no update or response. This is highly unusual for our account: I have shipped regular updates for over a year, and every single review has been completed within 24 hours. Something appears to be stuck on this specific submission. This is a major version that our partner venues are actively waiting on for a business-critical feature (in-app reservations), so the delay has a direct impact on us. Could the App Review team please look into why this submission is stalled? Case ID: [102945425814] Thank you.

Hi my app is still "Waiting for Review" since almost a week now. Is it normal? Thank you!

Hi, I just wanted to post to see if anyone else is experiencing extremely poor customer support from Apple. I have sent emails regarding the delay for the app review and heard nothing back, I have tried to call the worldwide support but get stuck in queues for over 3 hours before being disconnected. Has it always been this poor? My app has been stuck in review now for over a week despite it saying 48 hours, and whenever I try to reach out for help I receive no response. Could anyone please advise. Thank you!

This seems to be a reoccurring issue many developers are having and I was surprised because my app reviews used to take 12 hours max. However for my last submission, one of my apps is stuck at "In review" status for 3 weeks, despite my several expedite requests and open support case, no update on the status, no response to the communications and the worst part is that everywhere it is mentioned that the review is done within 1-2 days. And the other app was stuck at "Waiting for review" for about a week only to move to in review and get rejected in seconds with generic reason, I did the modifications and resubmitted knowing that it will not be an easy submission. One of the main concerns that my game got approved on other platforms and the players received a new version of the game while my iOS players are still stuck on the older one, the same for the other game which I newly launched. I hope Apple workes on fixing this.

Hi everyone,  I'm a relatively new developer and I just received my first App Store rejection. I'm posting here because I'm genuinely stuck and hoping the community can help me figure out where to even begin.  The Problem:  My app was rejected under Guideline 5.6 - Developer Code of Conduct - Review Suspended. The full message is the standard one: the app doesn't meet the "required quality standard," it's "not eligible for resubmission," and I should "ensure every screen, interaction, and piece of content has been thoughtfully designed" before submitting a new app.  Here's why I'm confused:  The rejection came with ZERO attachments. No screenshots. No screen recordings. No crash logs. No specific mention of a buggy feature, a broken button, or an unfinished screen. It's just a blanket statement about "quality" and "polish."  in my case, there's absolutely nothing to go on.  What I've checked so far:  I've tested the app on multiple physical devices (iPhone 12, 14, 15) – no crashes. I've reviewed every screen for placeholder text, "Lorem Ipsum," or dummy images – none found. I've checked the In-App Purchase / subscription screen for proper legal disclaimers and auto-renewal text – all present. I've made sure there are no debug logs or test toggles left in the production build. Everything looks fine to me, which is why I'm so lost. Without specific feedback, I don't know if the issue is:  A UI inconsistency I'm blind to? A subtle crash that only happens on a device I don't own? An issue with the paywall flow that I've misunderstood? Something about the metadata, screenshots, or app description? My questions for the community:  Has anyone else received a Guideline 5.6 rejection with no attachments? Is this common, or does it suggest the reviewer flagged the app as "low-quality" purely based on first impressions (like the design feels outdated or the concept is too simple)? Since the message says replies and resubmissions of this binary won't be reviewed, and I can't get clarification from the reviewer, what's the safest way to proceed? Should I:  Create a completely new App ID and submit as a new app? Or can I submit a new version under the same App ID? (I've heard mixed answers on this.) More importantly – how do I figure out what to fix? Without a starting point, I'm worried I'll fix the wrong things and get rejected again, which I know can lead to account termination after repeated violations. Are there any "hidden" quality checks that reviewers apply that aren't obvious to developers? For example, does Apple penalize apps that:  Have a generic icon or unpolished splash screen? Take too long to load on first launch? Have unclear navigation or confusing user flow? Lack a proper onboarding/tutorial for first-time users?   Thanks in advance for any help you can offer. I really want to get this right and not waste my one or two remaining chances. my app id : 6764726742

Hello, I have two subscriptions stuck in "Waiting for Review" status for 14 days now and I cannot update, edit or remove them. I emailed Apple Support 6 days ago with the specific details but have not received a response as yet. Is there anything I can do as this is blocking an app update. Thank you.

Hello Apple Developer Community, Our app has been waiting for App Review for approximately one week, and I would appreciate any guidance from developers who may have experienced a similar delay. App ID: 6789650549 The submission is still showing as “Waiting for Review.” We have checked the submission details, App Review information, subscription products, and required agreements, and we cannot identify anything missing or requiring action from our side. We understand that review times can vary, but since the app has remained in the queue for a week without entering review, we wanted to ask whether this is currently considered normal or whether there may be an issue with the submission. Would you recommend continuing to wait, contacting App Review, or taking any other action? We would prefer not to remove and resubmit the build unless necessary, as this could potentially restart the review queue. Thank you for your help.

I have finished a new app that integrates Apple hosted background asset. I have tested and confirm that the assets are downloaded both locally and with a TestFlight build. App review is not able to access the background assets. I can see that the assets are updated with status "accepted". But app review is running into error "A server with the specified hostname could not be found.". These are Apple Hosted Assets. Did I miss any configuration?

We are building a KPI(Telemetry) analytics reporting feature in our iOS app that requires recording and publishing reliable timestamps back to our backend server. Standard system time (Date()) is not suitable for our use case because it is susceptible to manual user changes (system clock manipulation) as well as clock drift over time. We are considering clock_gettime_nsec_np(CLOCK_MONOTONIC_RAW ) as a potential solution for iOS 10+. However, we want to confirm: Is clock_gettime_nsec_np a reliable, drift-free source for this purpose? Does the underlying OS handle NTP synchronization for these clocks, or can user-level time changes still impact them? Additionally, we recently came across Apple's official swift-ntp client library to fetch true NTP time directly. For production KPI reporting, is relying on an NTP library like swift-ntp the recommended approach, or is clock_gettime_nsec_np sufficient on modern iOS? We’d appreciate any insights or past experiences from the community. Thanks!

Hey everyone, I'm dealing with a strange issue with auto-renewable subscriptions in my app, and hoping someone can help or point me to the right direction. Here's what happened: Earlier I got my initial app version approved and released with monthly and yearly subscriptions in App Store Connect. And I checked that the app went live, and I could see the subscriptions in a fresh App Store install. But a few weeks after that, I noticed the subscriptions were gone from the app, then I went checking in App Store Connect, and found subscriptions were in some developer attention required state (something along the line). I then submitted a new app version with an additional subscription item, hoping I could reselect the prev 2 subscriptions and the new one for review, together with the new app build. And the subscriptions were in Waiting for Review status. But app reviewer responded that they can't see any subscription for review, and can't proceed with the review. And I noticed that the Subscriptions page shows the banner Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review., as if I had never got any subscription approved & released before. Now I'm completely stuck. App reviewer can't see the subscriptions, and I see in App Store Connect my subscriptions are in Waiting for Review status. Thanks a lot for any help!

Dear Apple Developer Support, I am requesting assistance regarding my Organization enrollment, which has been stuck in "Being Processed" for an extended period. I have already contacted Apple Developer Support three times through the Contact Us page. Each time, I received only the automatic acknowledgment email with a Case ID. Unfortunately, I have never received any follow-up from a support representative. Because of this, our company is currently unable to complete Organization Verification and cannot publish our iOS application on the App Store. Could you please: Check the status of my enrollment. Confirm whether my previous support requests were actually received by the Enrollment team. Escalate this case to the appropriate team if necessary. For your reference, my previous Case IDs are: Case ID: 102916885584 If you require any additional information or documentation from our company, please let me know. I will provide it immediately. Thank you for your time and assistance. I would greatly appreciate any update regarding the status of our Organization Verification. Kind regards, Dev UXUI Enrollment ID: WDF7RSUZ7P Company: Patana Intercool Company Limited

App Store Connect does not work. These forums do not work. Xcode does not work. Mac OS 26 navigation bars do not work. It's getting a little frustrating. App Store Connect: "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." How? I added a new app build (are "builds" and "versions" the same, I thought they were different, but why would I create a new version of my product?) and submitted it for review. It did not take the "Ready for Review" subscription items with it. They're stuck in a separate draft review. There is no control anywhere to "add an app version." Useless error, pathetic UI, designed by people who have never used this product themselves before, clearly. These forums: Try searching for "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." Get a 403 Forbidden error. Fun. Very useful. Xcode does not work. Spent a good part of my day debugging why Xcode will automatically mask Mac OS 12 icons when there is no Mac app icon specified in an asset collection in a Catalyst context, but will not mask the icon when there is a Mac icon specified. There's no messaging, no warnings, no errors, no nothing. It just does random things. The entire Catalyst idea is nice in theory but there are gotchas like these everywhere. Should you build for iOS, Mac, or iOS + Mac? The answer is "Good luck." Mac OS 26 navigation bars do not work. I'm getting black text on black backgrounds, white text on white backgrounds, sometimes, depending on whether a view loads. Seems like another Apple bug. Support is useless as always, and my record on these forums so far is that no one answers any of my questions. So I'm not sure why I bother. But maybe something I've written will help someone.

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

I submitted my app, PerkPulse, for review and it got rejected due to EULA agreement not being in app description, and for the subscriptions not being attached to the subscription. Currently, when I try to submit my app and two subscriptions, I get the error, "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." and it highlights one of my subscriptions. This is very frustrating and is blocking me from submitting my app for review. PerkPulse Pro Annually - product ID: app.perkpulse.mobile.pro_annual_v3 PerkPulse Pro Month - product ID: app.perkpulse.mobile.pro_monthly_v3 When I open the subscription group, it shows as "In Review", but I do not see any option for removing it from review so that I can attach my subscriptions. I have also had a phone call with apple support and could not get the issue resolved. I have: Deleted and recreated the subscriptions Checked all input fields, agreements to sign, etc. and cannot find an empty field Removed and re-added the subscriptions to draft submission Please any help would be appreciated.